Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RJD-1388/follow_trajectory #1449

Draft
wants to merge 78 commits into
base: master
Choose a base branch
from
Draft

RJD-1388/follow_trajectory #1449

wants to merge 78 commits into from

Conversation

robomic
Copy link
Contributor

@robomic robomic commented Nov 13, 2024

To be added

@robomic robomic self-assigned this Nov 13, 2024
Copy link

Checklist for reviewers ☑️

All references to "You" in the following text refer to the code reviewer.

  • Is this pull request written in a way that is easy to read from a third-party perspective?
  • Is there sufficient information (background, purpose, specification, algorithm description, list of disruptive changes, and migration guide) in the description of this pull request?
  • If this pull request contains a destructive change, does this pull request contain the migration guide?
  • Labels of this pull request are valid?
  • All unit tests/integration tests are included in this pull request? If you think adding test cases is unnecessary, please describe why and cross out this line.
  • The documentation for this pull request is enough? If you think adding documents for this pull request is unnecessary, please describe why and cross out this line.

This was the source of a bug. In initialization it was hidden which functions used which members and wrong initialization order was used

Signed-off-by: Mateusz Palczuk <[email protected]>
Signed-off-by: Mateusz Palczuk <[email protected]>
Signed-off-by: Mateusz Palczuk <[email protected]>
Signed-off-by: Mateusz Palczuk <[email protected]>
…e polyline_trajectory_follower file to follow_trajectory

Signed-off-by: Mateusz Palczuk <[email protected]>
…e polyline_trajectory_follower file to follow_trajectory

Change include paths and include guards

Signed-off-by: Mateusz Palczuk <[email protected]>
Add "_" suffix to PolylineTrajectoryPositioner data fields

Modify distanceAlongLanelet function to take 2 different bounding boxes as arguments

Add comments on what data fields are implicitly required by functions used in PolylineTrajectoryPositioner constructor

Signed-off-by: Mateusz Palczuk <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants